Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(flux): update image nextcloud 32.6.0 β†’ 32.6.1 #207

Merged
merged 1 commit into from
Jan 8, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2025

This PR contains the following updates:

Package Update Change
nextcloud (source) patch 32.6.0 -> 32.6.1

Configuration

πŸ“… Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

β™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

πŸ”• Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor

github-actions bot commented Jan 8, 2025

--- clusters/main/kubernetes/apps/nextcloud/app Kustomization: flux-system/nextcloud HelmRelease: nextcloud/nextcloud

+++ clusters/main/kubernetes/apps/nextcloud/app Kustomization: flux-system/nextcloud HelmRelease: nextcloud/nextcloud

@@ -12,13 +12,13 @@

     spec:
       chart: nextcloud
       sourceRef:
         kind: HelmRepository
         name: truecharts
         namespace: flux-system
-      version: 32.6.0
+      version: 32.6.1
   interval: 15m
   values:
     cnpg:
       main:
         backups:
           credentials: s3

@github-actions github-actions bot merged commit b649730 into main Jan 8, 2025
3 checks passed
@renovate renovate bot deleted the renovate/flux-nextcloud-32.6.x branch January 8, 2025 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants